Skip to content

elaborating on the new target service and port selection functionality #80

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jan 28, 2022

Conversation

robertpatrick
Copy link
Member

No description provided.

Copy link
Member

@rosemarymarano rosemarymarano left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

minor edits

@@ -86,7 +86,9 @@ When editing a route:
- Use the `Name` field to set the route name.
- Use the `Virtual Host` and `Path Expression` fields to define the matching rules that determine which requests match this route.
- All requests in the defined rules are routed to the service specified by the `Target Service` field that resides in the namespace specified by the read-only
`Target Service Namespace` field and the port specified by the `Target Port` field. Once the domain has been deployed, you can also select the values from the drop down list.
`Target Service Namespace` field and the port specified by the `Target Port` field. Once the domain has been deployed, you can select the `Target Service`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Once -> After (from Oracle editors, once – don’t use to mean after; use only to mean less than twice.)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

@@ -86,7 +86,9 @@ When editing a route:
- Use the `Name` field to set the route name.
- Use the `Virtual Host` and `Path Expression` fields to define the matching rules that determine which requests match this route.
- All requests in the defined rules are routed to the service specified by the `Target Service` field that resides in the namespace specified by the read-only
`Target Service Namespace` field and the port specified by the `Target Port` field. Once the domain has been deployed, you can also select the values from the drop down list.
`Target Service Namespace` field and the port specified by the `Target Port` field. Once the domain has been deployed, you can select the `Target Service`
value from the drop-down list of available service in the WebLogic Kubernetes Operator domain's namespace. Once the `Target Service` is selected,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

available service -> available services
Once the Target Service is selected -> After the Target Service is selected

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

@robertpatrick robertpatrick merged commit 417da4f into main Jan 28, 2022
@robertpatrick robertpatrick deleted the target-svc-doc-change branch January 28, 2022 16:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants